Update Portal Publisher API examples with RELEASE activation
#96
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given that the MavenCentral deployer doesn't support snapshots, I updated the corresponding examples with
RELEASEactivation instead ofALWAYS.I wanted to do the same at
reference/pages/deploy/maven/maven-central.adoc, but I noticed it importsreference/partials/deploy/maven/yaml/common-head.adoc, so I'd just leave it like that.As a cosmetic point, I also updated the license year in the footer. It could have been a separate PR, but it seemed too much noise 🙂 let me know if you prefer to handle that differently.